x86/ioreq server: release the p2m lock after mmio is handled
authorYu Zhang <yu.c.zhang@linux.intel.com>
Fri, 7 Apr 2017 15:35:44 +0000 (17:35 +0200)
committerJan Beulich <jbeulich@suse.com>
Fri, 7 Apr 2017 15:35:44 +0000 (17:35 +0200)
commitd909cb99998cd63761e238c59e274450c7dacd8e
tree035e116ca450be882e04186bb0295ee957266b0a
parent44525c3dd6d502fc2b858da3576ec4add3f3a72c
x86/ioreq server: release the p2m lock after mmio is handled

Routine hvmemul_do_io() may need to peek the p2m type of a gfn to
select the ioreq server. For example, operations on gfns with
p2m_ioreq_server type will be delivered to a corresponding ioreq
server, and this requires that the p2m type not be switched back
to p2m_ram_rw during the emulation process. To avoid this race
condition, we delay the release of p2m lock in hvm_hap_nested_page_fault()
until mmio is handled.

Note: previously in hvm_hap_nested_page_fault(), put_gfn() was moved
before the handling of mmio, due to a deadlock risk between the p2m
lock and the event lock(in commit 77b8dfe). Later, a per-event channel
lock was introduced in commit de6acb7, to send events. So we do not
need to worry about the deadlock issue.

Signed-off-by: Yu Zhang <yu.c.zhang@linux.intel.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
xen/arch/x86/hvm/hvm.c